New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: on error, reset spawnedProcess #41033
Conversation
💖 Thanks for opening this pull request! 💖 We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix. Examples of commit messages with semantic prefixes:
Things that will help get your PR across the finish line:
We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks reasonable to me. Definitely valid to clear out spawnedProcess
and spawnedArgs
to make future calls possible after recovering from an error.
I was wondering about the potential for reject()
to be called twice, once each for the error
and exit
signals, so in case any other reviewers were curious -- this is safe. After a promise is resolved, subsequent calls to a promise resolve function are no-ops.
Congrats on merging your first pull request! 🎉🎉🎉 |
No Release Notes |
I was unable to backport this PR to "26-x-y" cleanly; |
I was unable to backport this PR to "27-x-y" cleanly; |
I was unable to backport this PR to "28-x-y" cleanly; |
I have automatically backported this PR to "29-x-y", please check out #41110 |
reset spawnedProcess instance in case of error
fix: on error, reset spawnedProcess (#41033) reset spawnedProcess instance in case of error Co-authored-by: Maikel Ortega Hernández <maikeloh@gmail.com>
Description of Change
For squirrel update in case of errors during the update the
exit
event listener may not be called resulting onspawnedProcess
remains defined in memory preventing further updates checks to run with success.Checklist
Release Notes
Notes: none